Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Related issue (if applicable): final fixes from #17625 (reply in thread)
It happens sometimes that the driver's state machine sends a command but the EVERY_SECOND also send a Wifi State before the reponse from the command was received. This seems to loose the MCU in limbos.
Now if a command is sent and no answer received, WifiState and others won't be sent from EVERY_SECOND unless a 200ms timeout expired
It happens that some MCU would reset the ESP if it doesn't receive Wifi State 4 (connected to cloud) which is normally sent only after MQTT is connected. But is MQTT is not used, this is never sent and the ESP is resetted by the MCU
Added a test to send Wifi State 4 as soon as Wifi is connected is MQTT is not enabled
Changed the timer type in TuyaSNS result from signed (%d) to unsigned (%u) following Integer overflow for TuyaMCU timers (uint16 vs. int16) #18048
Checklist:
NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass